Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes #2478 legacy auth queries missing values #2479

Merged

Conversation

andrewpmartinez
Copy link
Member

No description provided.

@andrewpmartinez andrewpmartinez requested review from a team as code owners October 11, 2024 19:11
@@ -90,6 +90,9 @@ func MapApiSessionAuthQueriesToRestEntity(ae *env.AppEnv, rc *response.RequestCo
MinLength: authQuery.MinLength,
Provider: authQuery.Provider,
TypeID: authQuery.TypeID,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see these fields populated in API session returned from /authenticate?method=cert call

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same with HA controller: /oidc/login/cert returns

{"authQueries":[{"id":"2u9E63jXaAn7wAvG6vPKWa","provider":"url","scopes":null,"typeId":"EXT-JWT"}]}

Copy link
Member Author

@andrewpmartinez andrewpmartinez Oct 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be odd for legacy, specifically in this PR, because there are tests in this PR that ensure that,

Can you confirm the correct ext-jwt-signer is being configured and used?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also added a set of OIDC value checks, and the values I put in seem to come out.

@qrkourier
Copy link
Member

seems to at least partially resolve #2478

@ekoby
Copy link
Member

ekoby commented Oct 11, 2024

seems to at least partially resolve #2478

#2474 seems like a wrong reference

@andrewpmartinez andrewpmartinez changed the title fixes #2474 legacy auth queries missing values fixes #2478 legacy auth queries missing values Oct 15, 2024
@andrewpmartinez andrewpmartinez force-pushed the fix.2478.legacy.auth.quers.ext.jwt.missing.values branch from 83812b4 to 17c4c93 Compare October 15, 2024 13:35
- adds OIDC property checks on auth queries
- adds legacy property checks on auth queries
@andrewpmartinez andrewpmartinez force-pushed the fix.2478.legacy.auth.quers.ext.jwt.missing.values branch from 17c4c93 to 5133cd7 Compare October 15, 2024 13:36
@andrewpmartinez
Copy link
Member Author

seems to at least partially resolve #2478

#2474 seems like a wrong reference

Fixed.

@andrewpmartinez andrewpmartinez merged commit 37f6788 into main Oct 15, 2024
32 of 33 checks passed
@andrewpmartinez andrewpmartinez deleted the fix.2478.legacy.auth.quers.ext.jwt.missing.values branch October 15, 2024 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants